As of now we do not have a go-to metric of LOS, so we must design one based on available heuristics.
To adequately measure level of service we must account for:
We could account for:
Bottom line: we need an objective metric that will guide all activity
Service levels and cost of delivery have a strong positive relationship. Because of this it will be impossible to achieve minimum costs and maximum service levels.
It is up to us to determine what an adequate level of service is, and how much we are willing to pay for it.
Currently we do not track certain vital data in the AS400. These include (1) start/end delivery windows, (2) static & semi-dynamic route templates, and (3) service window importance.
This process should be very easy, but it has been made incredibly difficult by Omnitrac’s poor engineering capability. The fact that we are talking about (paying them) them to create an extremely simple report (customer ID, start time, end time) is simply unacceptable. This should be easy, yet it is a huge obstacle for our IT team
There is no scenario in which we succeed at dynamic routing and improve service levels (not to mention conflict between merchandising/operations) where we do not institute start times for all drivers statewide.
It may be prudent to identify internal or external driver backups. This is an insurance policy, in the event we have more drivers quit than we anticipate.
We need guidance ASAP as to (1) who will collect time windows, (2) how often, (3) how the party will be held accountable, and (4) how it will be input to Roadnet.
Naive proposition:
Currently, operations’ inability to communicate driver arrival times accurately is costing the merchandising team time and money. These conflicts are on-going and preventable.
It would be prudent to issue preliminary communications to drivers, customers & sales to set expectations for when dynamic routing is live.
[OTHER COMPANY] highlighted that they could have saved considerable aches & pains if they had communicated more effectively upfront with their drivers and with their customers.
It would also be helpful to ask Sales not to set unrealistic expectations about delivery times to customers.
## $key
## [1] 1 2 3 4 5 6 7 8 9 10 11 12
##
## $description
## [1] "Enumerate Questions Final Consult"
## [2] "Final Roadnet Consultation Onsite"
## [3] "Document SOP & Parameters for Dynamic"
## [4] "Best Practices Inquiry w/ Current Users"
## [5] "Final Approval from Sales/Merchandising"
## [6] "Ensure All Backups Accounted For"
## [7] "Outline Plan to Sales; Gain Approval"
## [8] "Communicate Dynamic Plan to Drivers"
## [9] "Institute Starting Times for Drivers"
## [10] "Plan for Ongoing Collection of Windows"
## [11] "Dynamic Route Day's Orders; Document/Experiment"
## [12] "Go Live Dynamic Routing All Routes"
##
## $start
## [1] "2017-03-25 CDT" "2017-06-08 CDT" "2017-02-17 CST" "2017-05-31 CDT"
## [5] "2017-02-20 CST" "2017-03-17 CDT" "2017-05-11 CDT" "2017-04-21 CDT"
## [9] "2017-05-11 CDT" "2017-05-31 CDT" "2017-02-02 CST" "2017-07-15 CDT"
##
## $end
## [1] "2017-06-05 CDT" "2017-06-09 CDT" "2017-06-11 CDT" "2017-06-21 CDT"
## [5] "2017-07-01 CDT" "2017-07-01 CDT" "2017-07-07 CDT" "2017-07-15 CDT"
## [9] "2017-07-15 CDT" "2017-07-15 CDT" "2017-07-31 CDT" "2017-08-01 CDT"
##
## $done
## [1] 95 0 60 50 25 75 50 5 5 5 88 0
##
## $neededBy
## [1] NA NA NA NA NA NA NA NA NA NA NA NA
##
## attr(,"class")
## [1] "gantt"